H.A.R.I. Deterministic Governance EN·IT Private discussion
Platform Verticals — Football Verticals — From cradle to Moon Extensions Framework Private discussion →
Home/Extensions/Smart glasses & field interfaces
Extensions / 3.2

Smart glasses & field interfaces.

The right information, to the right person, at the right moment, in the right role. Nothing else. Surveillance and facial recognition are excluded by architecture.

01

The four-rights principle

The field interface exists to deliver one thing: the role-bound informational payload the wearer’s role requires for the moment they are in. Four properties, all required:

1
Right info.
What the role’s policy declares for the moment — not the operator’s full available data.
2
Right person.
The named, authenticated wearer assigned to the role, not a generic “user”.
3
Right moment.
Within the policy-defined window for the role’s current phase, not whenever a model fires.
4
Right role.
Bound to the role the wearer is currently fulfilling — not aggregated across their history.
02

Cognitive overload prevention by design

Field interfaces fail catastrophically when they overwhelm the wearer. The commitment is to under-deliver rather than over-deliver: if policy does not call for an item, it is not on the surface. The kernel actively suppresses payloads that would exceed the role’s per-moment envelope. Saturation is a governance failure, not a UX inconvenience.

03

Roles supported

OfficialsReferees, fourth officials, VAR officials — green/red overlay, offside and line support, minimal alerts.
Technical staffCoaches, performance staff.
MedicalTeam doctors, paramedics, on-call clinicians.
AnalystsTactical, performance, match-control.
Stadium safetyLead, deputies, phase coordinators.
StewardsZone leads, evacuation aides.
Emergency operatorsMedical command, security command, civic liaison.
04

Integration model

Integrates with the authorized hardware ecosystem when access is granted — federation-, league-, club- or public-safety-issued devices — under the same provider-management discipline as any other integration. Currently in field-testing as the Smart Assistant Referee track.

05

Not for surveillance, not for facial recognition

No facial recognition. No attendee identification. No identity payloads fed into the chain. Where a role’s policy requires identity information — the wearer’s own credential — it is delivered to the wearer alone and not retained beyond the session.

Architectural commitment
The interface is governance-output, not surveillance-input. Signals flow out to the wearer; signals do not flow in from the wearer’s environment for identification, profiling or scoring.
—

Status

Architecture-validated for the role-bound field interface model; the Smart Assistant Referee track is in field-testing. Pilot-ready when scoped with the operational principal whose mandate covers the deployment.

Engagement

Governance you can wear.

Federations, leagues and venue operators: the role envelope model is discussed pre-NDA; device integration follows under NDA.